SAP Transactions Introduction

For performing any kind of task in the SAP R/3 ERP system, a transaction is used. SAP provides a standard set of transactions to manipulate i.e insert, update, delete and display data in the system. But sometimes, the need to create a customer specific transaction may arise due to the following reasons

• Standard SAP may not support that task

• A particular transaction needs to be customized to suit the customer requirements.

A transaction is defined as a sequence of dynpros (sap term for screens) having input and output fields and corresponding processing logic behind them to perform a particular task.

From the above table it is clear that any customer specific transaction starts with a �Z�.

The various aspects of designing a �Z� transaction are explained in the rest of this tutorial document. Knowledge of basic ABAP programming and dynpro programming is essential to understand this document. Detailed explanation of programming concept for every element of a dynpro is avoided in order to reduce confusion.

Every transaction has a 4-character code assigned to it. To invoke the transaction the user needs to enter this transaction code in the command window. This takes the control to the first screen of the transaction.

The task to be performed is divided into sequence of screens that provide a forum to interact with the user. All the screens belong to a single ABAP program called a module pool (type M program)

Transaction to call an executable report (type I program). The flow is divided into 3 parts � data entry via selection screen, data processing using start-of-selection and data output � list processing using end-of-selection

The scope of this tutorial is to explain the concept of Dialog Transaction in detail, covering areas such as: